Delivering customer specified receipt types at checkout

ABSTRACT

The present invention extends to methods, systems, and computer program products for delivering customer specified receipt types at checkout. A customer specifies receipt delivery preferences at a mobile device (e.g., specifying delivery of a digital receipt and/or a paper receipt at checkout). The mobile device sends the customer&#39;s receipt delivery preferences to a receipt preferences database server for storage in a receipt preferences database. During a sales transaction, a point-of-sale (“POS”) system refers to the receipt preferences database (or a relevant portion thereof) to access the customer&#39;s receipt delivery preferences. Based on the customer&#39;s receipt delivery preferences, the point-of-sale (“POS”) system delivers appropriate types of receipts (e.g. digital and/or paper) to the customer.

RELATED APPLICATIONS

This application is related to U.S. application Ser. No. 13/595,889,filed Aug. 27, 2012. The application is incorporated herein by referencefor all purposes.

BACKGROUND

1. Field of the Invention

This invention relates generally to the field of electronic salestransactions, and, more particularly, to delivering customer specifiedreceipt types at checkout.

2. Related Art

In a variety of transactions, consumers or buyers of goods or servicestypically receive receipts from their respective merchants or serviceproviders as proof of existence of conducted transactions. Generally,receipts are issued by merchants and service providers for a number ofreasons including, for example, regulatory or tax reasons andconvenience purposes. A receipt provides information about acorresponding transaction for the purpose of providing all participantswith a trace or record of the transaction. Receipts can later be used bya consumer for various purposes including, for example, provingparticipation in a transaction for tax reporting purpose, productreturns, use as a claim ticket for a further transaction, provisioningwarranties, etc. Depending on a variety of factors, such as, forexample, items being purchased, business or personal purchase, amount ofpurchase, etc., a consumer may desire an electronic receipt and/or apaper receipt.

For in-store purchases, consumers generally obtain a paper receipt atthe point-of-sale. However, some point-of-sale systems also support thedelivery of digital receipts at the point-of-sale. Further, fortelephone or online purchases digital receipts are typically deliveredto a customer.

In some situations, receipt deliver mechanisms may be somewhat rigid andmay not allow a user to configure desired receipt types (e.g., digitaland/or paper) for use at checkout. For example, a conventionalpoint-of-sale (“POS”) system typically includes a POS terminal, one ormore peripheral devices (display monitor, receipt printer, barcodescanner, weigh scale, electronic signature pad) and a payment processorwith pin pad (for credit and debit cards). The data for salestransactions is usually stored in a storage device of the POS terminal,which may be uploaded to one of the remote transaction authorizationservers or another remote server of the credit/debit card companies.Although POS systems are well equipped for merchants to monitor andcollect transaction data from the POS system, the ability of thecustomer to input or extract useful information from the POS system istypically limited to pinpad interactions (entering tip amounts,obtaining additional cash back, etc.), and obtaining printed receipts,the format and content of which has been pre-determined by the merchant.

Further, POS systems are typically sold with a proprietary on-boardsoftware system that may be specific to the merchant's business. Themerchant may be able to make minor programming adjustments to adddiscount codes and other special offers, but may have limited ability toadd functionality to the POS system.

BRIEF DESCRIPTION OF THE DRAWINGS

The specific features, aspects and advantages of the present inventionwill become better understood with regard to the following descriptionand accompanying drawings where:

FIG. 1 illustrates an example block diagram of a computing device.

FIG. 2 illustrates an example computer architecture that facilitatesdelivering customer specified receipt types at checkout.

FIG. 3 illustrates a flow chart of an example method for deliveringcustomer specified receipt types at checkout.

FIG. 4 illustrates another example computer architecture thatfacilitates delivering customer specified receipt types at checkout.

FIG. 5 illustrates another flow chart of an example method fordelivering customer specified receipt types at checkout.

FIG. 6 illustrates an example schematic block diagram of a point-of-sale(“POS”) system.

FIG. 7 illustrates an example schematic block diagram of a network ofpoint-of-sale (“POS”) systems.

DETAILED DESCRIPTION

The present invention extends to methods, systems, and computer programproducts for delivering customer specified receipt types at checkout. Inthe following description of the present invention, reference is made tothe accompanying drawings, which form a part hereof, and in which isshown by way of illustration specific embodiments in which the inventionis may be practiced. It is understood that other embodiments may beutilized and structural changes may be made without departing from thescope of the present invention.

Within this description and following claims, “customer fingerprint” isdefined as an identifier for a customer. A customer fingerprint can beused to associate a customer with corresponding point-of-sale (“POS”)data.

Embodiments of the present invention may comprise or utilize a specialpurpose or general-purpose computer including computer hardware, suchas, for example, one or more processors and system memory, as discussedin greater detail below. Embodiments within the scope of the presentinvention also include physical and other computer-readable media forcarrying or storing computer-executable instructions and/or datastructures. Such computer-readable media can be any available media thatcan be accessed by a general purpose or special purpose computer system.Computer-readable media that store computer-executable instructions arecomputer storage media (devices). Computer-readable media that carrycomputer-executable instructions are transmission media. Thus, by way ofexample, and not limitation, embodiments of the invention can compriseat least two distinctly different kinds of computer-readable media:computer storage media (devices) and transmission media.

Computer storage media (devices) includes RAM, ROM, EEPROM, CD-ROM,solid state drives (“SSDs”) (e.g., based on RAM), Flash memory,phase-change memory (“PCM”), other types of memory, other optical diskstorage, magnetic disk storage or other magnetic storage devices, or anyother medium which can be used to store desired program code means inthe form of computer-executable instructions or data structures andwhich can be accessed by a general purpose or special purpose computer.

A “network” is defined as one or more data links that enable thetransport of electronic data between computer systems and/or modulesand/or other electronic devices. When information is transferred orprovided over a network or another communications connection (eitherhardwired, wireless, or a combination of hardwired or wireless) to acomputer, the computer properly views the connection as a transmissionmedium. Transmissions media can include a network and/or data linkswhich can be used to carry desired program code means in the form ofcomputer-executable instructions or data structures and which can beaccessed by a general purpose or special purpose computer. Combinationsof the above should also be included within the scope ofcomputer-readable media.

Further, upon reaching various computer system components, program codemeans in the form of computer-executable instructions or data structurescan be transferred automatically from transmission media to computerstorage media (devices) (or vice versa). For example,computer-executable instructions or data structures received over anetwork or data link can be buffered in RAM within a network interfacemodule (e.g., a “NIC”), and then eventually transferred to computersystem RAM and/or to less volatile computer storage media (devices) at acomputer system. RAM can also include solid state drives (SSDs or PCIxbased real time memory tiered Storage, such as FusionIO). Thus, itshould be understood that computer storage media (devices) can beincluded in computer system components that also (or even primarily)utilize transmission media.

Computer-executable instructions comprise, for example, instructions anddata which, when executed at a processor, cause a general purposecomputer, special purpose computer, or special purpose processing deviceto perform a certain function or group of functions. The computerexecutable instructions may be, for example, binaries, intermediateformat instructions such as assembly language, or even source code.Although the subject matter has been described in language specific tostructural features and/or methodological acts, it is to be understoodthat the subject matter defined in the appended claims is notnecessarily limited to the described features or acts described above.Rather, the described features and acts are disclosed as example formsof implementing the teachings.

Those skilled in the art will appreciate that the invention may bepracticed in network computing environments with many types of computersystem configurations, including, personal computers, desktop computers,laptop computers, message processors, hand-held devices, multi-processorsystems, microprocessor-based or programmable consumer electronics,network PCs, minicomputers, mainframe computers, mobile telephones,PDAs, tablets, pagers, routers, switches, various storage devices, andthe like. The invention may also be practiced in distributed systemenvironments where local and remote computer systems, which are linked(either by hardwired data links, wireless data links, or by acombination of hardwired and wireless data links) through a network,both perform tasks. In a distributed system environment, program modulesmay be located in both local and remote memory storage devices.

Embodiments of the invention can also be implemented in cloud computingenvironments. In this description and the following claims, “cloudcomputing” is defined as a model for enabling ubiquitous, convenient,on-demand network access to a shared pool of configurable computingresources (e.g., networks, servers, storage, applications, and services)that can be rapidly provisioned via virtualization and released withminimal management effort or service provider interaction, and thenscaled accordingly. A cloud model can be composed of variouscharacteristics (e.g., on-demand self-service, broad network access,resource pooling, rapid elasticity, measured service, etc.), servicemodels (e.g., Software as a Service (SaaS), Platform as a Service(PaaS), Infrastructure as a Service (IaaS), and deployment models (e.g.,private cloud, community cloud, public cloud, hybrid cloud, etc.).Databases described with respect to the presented invention can beincluded in a cloud model.

It is further noted that, where feasible, functions described herein canbe performed in one or more of: hardware, software, firmware, digitalcomponents, or analog components. For example, one or more applicationspecific integrated circuits (ASICs) can be programmed to carry out oneor more of the systems and procedures described herein. Certain termsare used throughout the following description and Claims to refer toparticular system components. As one skilled in the art will appreciate,components may be referred to by different names. This document does notintend to distinguish between components that differ in name, but notfunction.

In general, embodiments of the invention are directed to deliveringcustomer specified receipt types at checkout. A customer specifiesreceipt delivery preferences at a mobile device (e.g., specifyingdelivery of a digital receipt and/or a paper receipt at checkout). Themobile device sends the receipt delivery preferences to a receiptpreferences database server. The receipt preferences database serverstores an association between the receipt delivery preferences and acustomer fingerprint in a receipt preferences database.

Subsequently, the customer can participate in a sales transaction at astore location. As part of the sales transaction, a point-of-sale (POS)system generates receipt data. The point-of-sale (POS) system and thereceipt preferences database server interoperate with one another todeliver appropriate receipt types (e.g., digital and/or paper)containing the receipt data.

In some embodiments, the receipt preferences database (or relevantportion thereof) is synced to the point-of-sale (POS) system from timeto time. During checkout, a customer provides data for deriving acustomer fingerprint to the point-of-sale (POS) system (e.g., by swipinga loyalty card, entering a number on a pin pad, etc.). The point-of-sale(POS) system uses the provided data to derive a customer fingerprint forthe customer. The point-of-sale (“POS”) system uses the customerfingerprint to locate associated receipt delivery preferences fromwithin the synced receipt preferences database. At the close of a salestransaction, receipts are delivered in accordance with the associatedreceipt delivery preferences. For example, the point-of-sale (“POS”)system can send a digital receipt to a mobile device and/or can print apaper receipt.

In other embodiments, the point-of-sale (“POS”) system has an openconnection to the receipt preferences database server. In these otherembodiments, a customer fingerprint is derived and is used to poll thereceipt preferences database server for associated receipt deliverypreferences. The receipt preferences database server uses the customerfingerprint to locate the associated receipt delivery preferences fromwithin the receipt preferences database. The receipt preferencesdatabase server then returns the associated receipt delivery preferencesback to the point-of-sale (“POS”) system. At the close of a salestransaction, receipts are delivered in accordance with the associatedreceipt delivery preferences. For example, the point-of-sale (“POS”)system can send a digital receipt to a mobile device and/or can print apaper receipt.

The point-of-sale (“POS”) system can poll the receipt preferencesdatabase server at specified intervals (e.g., every second) prior to asales transaction closing. As such, in the event a customer changesspecified receipt delivery preferences during a sales transaction, thereis an increased chance that the point-of-sale (“POS”) system can deliverreceipts in accordance with more recently specified receipt deliverypreferences.

FIG. 1 illustrates an example block diagram of a computing device 100.Computing device 100 can be used to perform various procedures, such asthose discussed herein. Computing device 100 can function as a server, aclient, or any other computing entity. Computing device 100 can performvarious communication and data transfer functions as described hereinand can execute one or more application programs, such as theapplication programs described herein. Computing device 100 can be anyof a wide variety of computing devices, such as a mobile telephone orother mobile device, a desktop computer, a notebook computer, a servercomputer, a handheld computer, tablet computer and the like.

Computing device 100 includes one or more processor(s) 102, one or morememory device(s) 104, one or more interface(s) 106, one or more massstorage device(s) 108, one or more Input/Output (I/O) device(s) 110, anda display device 130 all of which are coupled to a bus 112. Processor(s)102 include one or more processors or controllers that executeinstructions stored in memory device(s) 104 and/or mass storagedevice(s) 108. Processor(s) 102 may also include various types ofcomputer-readable media, such as cache memory.

Memory device(s) 104 include various computer-readable media, such asvolatile memory (e.g., random access memory (“RAM”) 114) and/ornonvolatile memory (e.g., read-only memory (“ROM”) 116). Memorydevice(s) 104 may also include rewritable ROM, such as Flash memory.

Mass storage device(s) 108 include various computer readable media, suchas magnetic tapes, magnetic disks, optical disks, solid state memory(e.g., Flash memory), and so forth. As shown in FIG. 1, a particularmass storage device is a hard disk drive 124. Various drives may also beincluded in mass storage device(s) 108 to enable reading from and/orwriting to the various computer readable media. Mass storage device(s)108 include removable media 126 and/or non-removable media.

I/O device(s) 110 include various devices that allow data and/or otherinformation to be input to or retrieved from computing device 100.Example I/O device(s) 110 include cursor control devices, keyboards,keypads, microphones, monitors or other display devices, speakers,sensors, printers, network interface cards, modems, cameras, lenses,CCDs or other image capture devices, and the like.

Display device 130 includes any type of device capable of displayinginformation to one or more users of computing device 100. Examples ofdisplay device 130 include a monitor, display terminal, video projectiondevice, and the like.

Interface(s) 106 include various interfaces that allow computing device100 to interact with other systems, devices, or computing environments.Example interface(s) 106 can include any number of different networkinterfaces 120, such as interfaces to personal area networks (“PANs”),local area networks (“LANs”), wide area networks (“WANs”), wirelessnetworks (e.g., near field communication (“NFC”), Bluetooth, Wi-Fi, etc.networks), and the Internet. Other interfaces include user interface 118and peripheral device interface 122.

Bus 112 allows processor(s) 102, memory device(s) 104, interface(s) 106,mass storage device(s) 108, and I/O device(s) 110 to communicate withone another, as well as other devices or components coupled to bus 112.Bus 112 represents one or more of several types of bus structures, suchas a system bus, PCI bus, IEEE 1394 bus, USB bus, and so forth.

FIG. 2 illustrates an example computer architecture 200 that facilitatesdelivering customer specified receipt types at checkout. Referring toFIG. 2, computer architecture 200 includes mobile device 201, POS system211, and receipt preferences database server 221. Each of the depictedcomponents can be connected to one another over (or be part of) anetwork, such as, for example, a PAN, a LAN, a WAN, and even theInternet. Accordingly, each of the depicted components as well as anyother connected computer system and their component, can create messagerelated data and exchange message related data over the network. Forexample, message related data may include, but is not limited to, nearfield communication (“NFC”) payloads, Bluetooth packets, InternetProtocol (IP) datagrams and other higher layer protocols that utilize IPdatagrams, such as, Transmission Control Protocol (TCP), HypertextTransfer Protocol (HTTP), Simple Mail Transfer Protocol (SMTP), etc.

As depicted, mobile device 201 (e.g. a smartphone) further includesreceipt preferences application 202 and communication module 203.Generally, receipt preferences application 202 is configured to managereceipt preferences (e.g., a desire for digital and/or paper receipts)for user of mobile device 201. Receipt preferences application 202 canalso be used to pair customer fingerprint 243 (e.g., derived from aloyalty number, a telephone number, a portion of a credit card number,biometric information, etc.) with mobile device 201. As such, electronicreceipts corresponding to customer fingerprint 243 can be delivered tomobile device 201.

Receipt preferences application 202 can include a user-interface andmemory permitting a customer to enter, store, and change receiptdelivery preferences 244. For example, customer 291 can enter and/orchange receipt delivery preferences 244 to enable or disable printing ofa paper receipt for sales transactions. A customer can specify thatpaper receipts are always to be printed, never to be printed, printed atcertain locations but not at other locations, printed only for a nextsales transaction, etc.

Communication module 203 can be a wireless network adapter forconnecting mobile device 201 with a wireless network, such as, forexample, Wi-Fi and/or a cellular network (e.g., CDMA, GSM, iDen, etc.)that facilitates a further connection to network 251 (e.g., theInternet).

As depicted, POS system 211 includes transaction processor 212,communication module 213, and I/O peripherals 216. POS system 211 can bephysically located at a checkout lane in a store. Generally, transactionprocessor 212 is configured to manage sales transactions for POS 211.Transaction processor 212 can receive input from I/O peripherals 216 toopen a sales transaction, collect receipt data (e.g., date, time, item,and cost data, etc.) for a sales transaction, and close a salestransaction. Receipt data for an item (e.g. item description and itemcost) can be retrieved from an item database in response to scanning abarcode on (or otherwise identifying) the item. I/O peripherals 216 caninclude one or more of: a monitor (e.g., a cashier-facing monitor), oneor more input devices (e.g., scanners, keyboards, scales, or the like),one or more payment devices (e.g., cash drawers, card readers, etc.) forreceiving or returning payments, and one or more output devices (e.g.,customer-facing display or monitor, receipt printer, etc.).

Communication module 213 can include a wired and/or wireless networkadapter for connecting mobile device 201 with a network, such as, forexample, a Wi-Fi and/or wired Ethernet network, that facilitates afurther connection to network 251 (e.g., the Internet).

POS system 211 can be in a physical store location that is owned by anentity, such as, for example, a retailer corporation that operates achain of stores. The chain of stores can include one or more of: grocerystores, department stores, warehouse stores, discount stores, etc. Insome embodiments, POS system 211 includes components in a checkout isleas well as components in a store based data center.

As depicted, receipt preferences database server 221 includes Web server241, communication module 242, and database access module 263. Inoperation, web server 241 is configured to communicate with externaldevices, such as, for example, mobile device 201. Communication module242 is configured to communicate with other systems that are commonlyowned by the same entity as receipt preferences database server 221. Forexample, an entity can own one or more physical store locations (e.g. achain of stores). Each of the one or more store locations can includeone or more POS systems 211. Receipt preferences database server 221 canuse communication module 242 to communicate with POS systems 211 at theone or more store locations.

Database access module 263 is configured to manage receipt preferencesdatabase 272. Receipt preferences database 222 stores receipt deliverypreferences for customers that conduct sales transactions at the one ormore store locations. Receipt preferences database server 221 can usedatabase access module 263 to receive receipt delivery preferences for acustomer from a mobile device through web server 241. Receiptpreferences database server 221 can also use database access module 263to store received receipt delivery preferences in receipt preferencesdatabase 222.

Receipt preferences data server 221 can be owned by the same entity(e.g., a retailer corporation) that owns POS system 211. The same entitycan also own one or more other POS systems similar to POS system 211.Receipt preferences data server 221 can communicate with POS system 211and any of the one or more other POS systems to facilitate businessoperations for the entity.

Thus, from time to time, relevant portions of receipt preferencesdatabase 222 can be synced to POS system 211 or another POS system andcached for local access. For example, for a POS system at a particularstore location, portions of receipt preferences database 222 relevant tothe particular store location can be synced to the POS system. The POSsystem can then access receipt delivery preferences for a customerlocally and deliver receipts to the customer in accordance with theirspecified receipt delivery preferences (e.g., sending a digital receiptto a mobile device and/or printing a paper receipt).

FIG. 3 illustrates a flow chart 300 of an example method for deliveringcustomer specified receipt types at checkout. Method 300 will bedescribed with respect to the components and data of computerarchitecture 200.

Method 300 includes receiving customer input specifying receipt deliverypreferences that apply to sales transactions conducted with an entity,the specified receipt delivery preferences including a printed receiptpreference for one or more of the entity's store locations, the printedreceipt preference indicating if a customer desires printed receipts fortransactions (301). For example, mobile device 201 can receive input 292from customer 291. Input 292 can specify receipt delivery preferences244 for sales tractions conducted with POS system 211, as well as othercommonly owned POS systems. Receipt delivery preferences 244 can includea printed receipt preference indicating if customer 291 desires printedreceipts for sales transactions. For example, receipt deliverypreferences 244 can specify that customer 291 always wants paperreceipts, never wants paper receipts, wants paper receipts at somelocations but not at other locations, wants a paper receipt just for thenext sales transaction, wants a paper receipt when a sales transactionexceeds a threshold amount (e.g., $75.00 or over), etc. Receipt deliverypreferences 244 can also specify that customer 291 always wants digitalreceipts, never wants digital receipts, wants digital receipts at somelocations but not at other locations, wants a digital receipt just forthe next sales transaction, wants a digital receipt when a salestransaction is below a threshold amount (e.g., under $75.00), etc.

Method 300 includes sending a customer fingerprint along with thecustomer specified receipt delivery preferences to a receipt preferencesdatabase server (302). For example, communication module 203 can sendcustomer fingerprint 243 (a customer fingerprint associated withcustomer 291) along with receipt delivery preferences 244 to receiptpreferences database server 221. Customer fingerprint 243 can be derivedfrom fingerprint input data 293 including one or more of: a loyalty cardnumber, portions of a credit card number, a phone number, biometricdata, etc. In one example, receipt preferences application 202 caninclude a fingerprint generation algorithm that processes fingerprintinput data 293 to derive customer fingerprint 243 for customer 291.Customer 291 can enter fingerprint input data 293 at mobile device 201(e.g., a loyalty card number or a portion of a credit card number) Inanother example, mobile device 201 can obtain fingerprint input datainternally (e.g., a telephone number associated with mobile device 201).

Method 300 includes receiving the customer fingerprint and customerspecified receipt delivery preferences from the mobile device (303). Forexample, Web server 241 can receive customer fingerprint 243 along withreceipt delivery preferences 244 from mobile device 201.

Method 300 includes storing an association between the customerfingerprint and the customer specified receipt delivery preferences in areceipt preferences database, the receipt preferences database storingcustomer specified receipt delivery preferences for a plurality ofdifferent customers (304). For example, database access module 263 canstore an association between customer fingerprint 243 and receiptdelivery preferences 244 in receipt preferences database 222. Receiptpreferences database 222 can also store receipt delivery preferences forone or more other customers.

For each customer, a customer fingerprint can be associated with thecustomer's specified receipt delivery preferences. For example, for someother customer, another mobile device can derive customer fingerprint246 (e.g., using the same fingerprint generation algorithm) and receiveinput specifying receipt delivery preferences 247. The other mobiledevice can send customer fingerprint 246 along with receipt deliverypreferences 247 to receipt preferences database server 221. Databaseaccess module 263 can store an association between customer fingerprint246 and receipt delivery preferences 247 in receipt preferences database222.

Method 300 includes syncing a relevant portion of the receiptpreferences database to each of the one or more store locations (305)and syncing a relevant portion of the receipt preferences database fromthe receipt preferences database server (306). For example, databaseportion 248 (of receipt preferences database 222) can be synced fromreceipt preferences database server 221 to POS system 211. Databaseportion 248 can include receipt delivery preferences corresponding tothe store (physical) location of POS system 211. Other portions ofreceipt preferences database 222 can be synced to other store locations.In some embodiments, receipt preferences database 222 is synced in itsentirety to each of the one or more store locations.

Method 300 includes opening a sales transaction for a customer (307).For example, customer 291 can make one or more items they wish topurchase available to a cashier. The cashier can then process (e.g.,scan) each of the items as part of a checkout procedure. Alternately,the customer 291 can process (e.g., scan) each of the one or more itemshimself or herself as part of a self-checkout procedure. As part of thecheckout process, customer 291 or a cashier can enter commands at I/Operipherals 216 to start a new sales transaction. In response, I/Operipherals 216 can send open transaction message 232 to transactionprocessor 212. Transaction processor 212 can receive open transactionmessage 232 from I/O peripherals 216. In response to open transactionmessage 232, transaction processor 212 can open a sales transaction toprocess the one or more items for customer 291.

Method 300 includes subsequent to opening the sales transaction,collecting receipt data for the sales transaction (308). For example, inresponse to opening the sales transaction, transaction processor 212 cancollect receipt data 233 for each of the one or more items that isprocessed (e.g., scanned) during the sales transaction.

Method 300 includes deriving a customer fingerprint associated with thesales transaction (309). For example, customer 291 can use an I/Operipheral from among I/O peripherals 216 (e.g., a card reader or pinpad) to enter fingerprint input data 293 into POS system 211. POS system211 can use the same fingerprint generation algorithm as mobile device201 to derive customer fingerprint 243 from fingerprint input data 293.

Method 300 includes using the customer fingerprint to locate applicablereceipt delivery preferences, including a printed receipt preference,for the sales transaction from within the synced portion of the receiptpreferences database (310). For example, transaction processor 212 canuse customer fingerprint 243 to locate receipt delivery preferences 244from within database portion 248. As described, receipt deliverypreferences 244 includes a printed receipt preference indicating whetheror not customer 291 desires a printed receipt for the sales transaction.

Method 300 includes closing the sales transaction (311). For example,when each of the one or more items has been processed (e.g., scanned), acashier or customer 291 can enter commands at I/O peripherals 216 to endthe sales transaction. In response, I/O peripherals 216 can send closetransaction message 234 to transaction processor 212. Transactionprocessor 212 can receive close transaction message 234 from I/Operipherals 216. In response to close transaction message 234,transaction processor 212 can close the sales transaction processing theone or more items for customer 291.

Method 300 includes in response to closing the sales transaction,outputting one or more types of receipts for the sales transaction(312). For example, in response to closing the sales transaction forcustomer 291, POS system 211 can output one or more types of receipts,such as, for example, digital and/or printed receipts, for the salestransaction.

Outputting one or more types of receipts for the sales transaction caninclude sending a digital receipt containing the collected receipt datato a mobile device that was previously paired to the customerfingerprint (313). For example, POS system 211 can send digital receipt261, including receipt data 233, to mobile device 201. Alternately, POSsystem 211 can send digital receipt 261, including receipt data 233, toreceipt preferences database server 221. Receipt preferences databaseserver 221 can store digital receipt 261. Receipt preferences databaseserver 221 can also store an association between customer fingerprint243 and receipt 261.

Outputting one or more types of receipts for the sales transaction caninclude printing a paper receipt containing the collected receipt datain accordance with the printed receipt preference (314). In someembodiments, receipt delivery preferences 244 specify that a paperreceipt is desired for the sales transaction. In these embodiments, anI/O peripheral, such as, for example, a receipt printer in I/Operipherals 216, can print receipt data 233 in paper receipt 262. Inother embodiments, receipt delivery preferences 244 specify that aprinted receipt is not desired for the sales transaction. In these otherembodiments, a paper receipt is not printed.

Method 300 includes receiving the digital receipt from the Point-Of-Sale(POS) system (315). For example, mobile device 201 can receive digitalreceipt 261, including receipt data 233, from POS system 211.Alternately, mobile device 201 can request digital receipts from receiptpreferences database server 221. For example, mobile device 201 can senda request to receipt preferences database server 221 for any digitalreceipts associated customer fingerprint 243. In response, receiptpreferences database server 201 can return digital receipts associatedwith customer fingerprint 243, including digital receipt 261, back tomobile device 201. Customer 291 can then view receipt data 233 on mobiledevice 201.

In embodiments where paper receipt 262 is printed, customer 291 can alsoobtain paper receipt 262, either directly (e.g., when doingself-checkout) or from a cashier.

FIG. 4 illustrates an example computer architecture 400 that facilitatesdelivering customer specified receipt types at checkout. Referring toFIG. 4, computer architecture 400 includes mobile device 401, POS system411, and receipt preferences database server 421. Each of the depictedcomponents can be connected to one another over (or be part of) anetwork, such as, for example, a PAN, a LAN, a WAN, and even theInternet. Accordingly, each of the depicted components as well as anyother connected computer systems and their components, can createmessage related data and exchange message related data (e.g., near fieldcommunication (“NFC”) payloads, Bluetooth packets, Internet Protocol(“IP”) datagrams and other higher layer protocols that utilize IPdatagrams, such as, Transmission Control Protocol (“TCP”), HypertextTransfer Protocol (“HTTP”), Simple Mail Transfer Protocol (“SMTP”),etc.) over the network.

As depicted, mobile device 401 (e.g., a smartphone) further includesreceipt preferences application 402 and communication module 403.Generally, receipt preferences application 402 is configured to managereceipt preferences (e.g., a desire for digital and/or paper receipts)for user of mobile device 401. Receipt preferences application 402 canalso be used to pair customer fingerprint 443 (e.g., data derived from aloyalty number, telephone number, a portion of a credit card number,biometric information, etc.) with mobile device 401. As such, electronicreceipts corresponding to customer fingerprint 443 can be delivered tomobile device 401.

Receipt preferences application 402 can include a user-interfacepermitting a customer to enter and change receipt delivery preferences.For example, customer 491 can enter and/or change receipt deliverypreferences to enable or disable printing of a paper receipt for salestransactions. A customer can specify that paper receipts are always tobe printed, never to be printed, printed at certain locations but not atother locations, printed only for a next sales transaction, etc.

Communication module 403 can be a wireless network adapter forconnecting mobile device 201 with a wireless network, such as, forexample, Wi-Fi and/or a cellular network (e.g., CDMA, GSM, iDen, etc.)that facilitates a further connection to network 451 (e.g., theInternet).

As depicted, POS system 411 includes transaction processor 412,communication module 413, and I/O peripherals 416. POS 411 can bephysically located at a checkout lane in a store. Generally, transactionprocessor 412 is configured to manage sales transactions for POS 411.Transaction processor 412 can receive input from I/O peripherals 416 toopen a sales transaction, collect receipt data (e.g., date, time, item,and cost data, etc.) for a sales transaction, and close a salestransaction. Receipt data for an item (e.g. item description and itemcost) can be retrieved from an item database in response to scanning abarcode on (or otherwise identifying) the item. I/O peripherals 416 caninclude one or more of: a monitor (e.g., a cashier-facing monitor), oneor more input devices (e.g., scanners, keyboards, scales, or the like),one or more payment devices (e.g., cash drawers, card readers, etc.) forreceiving or returning payments, and one or more output devices (e.g.,customer-facing display or monitor, receipt printer, etc.).

Communication module 413 can be a wired and/or wireless network adapterfor connecting mobile device 401 with a network, such as, for example, aWi-Fi and/or wired Ethernet network, that facilitates a furtherconnection to network 451 (e.g., the Internet).

POS system 411 can be in a physical store location that is owned by anentity, such as, for example, a retailer corporation that runs a chainof stores. The chain of stores can include one or more of: grocerystores, department stores, warehouse stores, discount stores, etc. Inembodiments, POS system 411 includes components in a checkout isle aswell as components in a store based data center.

As depicted, receipt preferences data server 421 includes Web server441, communication module 442, and database access module 463. Webserver 441 is configured to communicate with external devices, such as,for example, mobile device 401. Communication module 441 is configuredto communicate with other systems that are commonly owned by the sameentity as receipt preferences database server 421. For example, anentity can own one or more physical store locations (e.g. a change ofstores). Each of the one or more store locations can include one or morePOS systems 411. Receipt preferences database server 421 can usecommunication module 442 to communicate with POS systems at the one ormore store locations.

Database access module 463 is configured to manage receipt preferencesdatabase 472. Receipt preferences database 472 stores receipt deliverypreferences for customers that conduct sales transactions at the one ormore store locations. Receipt preferences database server 421 canreceive receipt deliver preferences for a customer from a mobile devicethrough Web server 441. Receipt preferences database server 421 can usedatabase access module 463 to store received receipt deliverypreferences in receipt preferences database 422.

Receipt preferences database server 421 can be owned by the same entity(e.g., a retailer corporation) that owns POS system 411. The same entitycan also own one or more other POS systems similar to POS system 411.Receipt preferences database server 421 can communicate with POS system411 and any of the one or more other POS systems to facilitate businessoperations for the entity.

Thus, from time to time, POS systems, such as, for example, POS system411, can poll receipt preferences database server 421 to obtain storedreceipt delivery preferences for a customer. Receipts can be deliveredto the customer in accordance with the receipt delivery preferences(e.g., sending a digital receipt to a mobile device and/or printing apaper receipt). In some embodiments, a POS system polls receiptpreferences database server 421 at specified intervals (e.g., everysecond). Thus, if a customer changes receipt delivery preferences duringa sales transaction, there is an increased chance that more recentreceipt delivery preferences can be detected prior to closing the salestransaction. The POS system can then deliver receipts to the customer inaccordance with the more recent receipt delivery preferences.

FIG. 5 illustrates a flow chart of an example method 500 for deliveringcustomer specified receipt types at checkout. Method 500 will bedescribed with respect to the components and data of computerarchitecture 400.

Method 500 includes receiving customer input specifying receipt deliverypreferences that apply to sales transactions conducted with an entity,the specified receipt delivery preferences including printed receiptpreferences for one or more of the entity's store locations, the printedreceipt preferences indicating if a customer desires printed receiptsfor transactions (501). For example, mobile device 401 can receive input492 from customer 491. Input 492 can specify receipt deliverypreferences 444 for sales tractions conducted with POS system 411, aswell as other commonly owned POS systems. Receipt delivery preferences444 can include a printed receipt preference indicating if customer 491desires printed receipts for sales transactions. For example, receiptdelivery preferences 444 can specify that customer 491 always wantspaper receipts, never wants paper receipts, wants paper receipts at somelocations but not at other locations, wants a paper receipt just for thenext sales transaction, wants a paper receipt when a sales transactionexceeds a threshold amount (e.g., $75.00), etc.

Method 500 includes sending a customer fingerprint along with thecustomer specified receipt delivery preferences to a receipt preferencesdatabase server (502). For example, communication module 403 can sendcustomer fingerprint 443 (a customer fingerprint associated withcustomer 491) along with receipt delivery preferences 444 to receiptpreferences database server 421. Customer fingerprint 443 can be derivedfrom fingerprint input data 493 including one or more of: a loyalty cardnumber, portions of a credit card number, a phone number, etc. Receiptpreferences application 402 can include a fingerprint generationalgorithm that processes fingerprint input data 493 to derive customerfingerprint 443 for customer 491. In another example, mobile device 401can obtain fingerprint input data internally (e.g., a telephone numberassociated with mobile device 401).

Method 500 includes receiving the customer finger print and customerspecified receipt delivery preferences from the mobile device (503). Forexample, Web server 441 can receive customer fingerprint 443 along withreceipt delivery preferences 444 from mobile device 401.

Method 500 includes storing an association between the customerfingerprint and the customer specified receipt delivery preferences in areceipt preferences database, the receipt preferences database storingcustomer specified receipt delivery preferences for a plurality ofdifferent customers (504). For example, database access module 463 canstore an association between customer fingerprint 443 and receiptdelivery preferences 444 in receipt preferences database 422. Receiptpreferences database 442 can also store receipt delivery preferences forone or more other customers.

For each customer, a customer fingerprint can be associated with thecustomer's specified receipt delivery preferences. For example, for someother customer, another mobile device can derive customer fingerprint446 (e.g., using the same fingerprint generation algorithm) and receiveinput specifying receipt delivery preferences 447. The other mobiledevice can send customer fingerprint 446 along with receipt deliverypreferences 447 to receipt preferences database server 421. Databaseaccess module 463 can store an association between customer fingerprint446 and receipt delivery preferences 447 in receipt preferences database422.

Method 500 includes opening a sales transaction for a customer (505).For example, customer 491 can make one or more items they wish topurchase available to a cashier. The cashier can then process (e.g.,scan) each of the items as part of a checkout procedure. Alternately,the customer 491 can process (e.g., scan) each of the one or more itemshimself or herself as part of a self-checkout procedure. As part of thecheckout process, customer 491 or a cashier can enter commands at I/Operipherals 416 to start a new sales transaction. In response, I/Operipherals 416 can send open transaction message 432 to transactionprocessor 412. Transaction processor 412 can receive open transactionmessage 432 from I/O peripherals 416. In response to open transactionmessage 432, transaction processor 412 can open a sales transaction toprocess the one or more items for customer 491.

Method 500 includes subsequent to opening the sales transaction,collecting receipt data for the sales transaction (506). For example, inresponse to opening the sales transaction, transaction processor 412 cancollect receipt data 433 for each of the one or more items that isprocessed (e.g., scanned) during the sales transaction.

Method 500 includes accessing a customer fingerprint associated withsales transaction (507). For example, customer 491 can use an I/Operipheral from among I/O peripherals 416 (e.g., a card reader or pinpad) to enter fingerprint input data 493 into POS system 411. POS system411 can use the same fingerprint generation algorithm as mobile device401 to derive customer fingerprint 443 from fingerprint input data 493.

Method 500 includes polling the receipt preferences database server forreceipt delivery preferences applicable to the sales transaction, thepoll including the customer fingerprint (508). Method 500 includesreceiving the poll for receipt delivery preferences from a Point-Of-Sale(POS) system at one of the entity's store locations, the poll forreceipt delivery preferences applicable to the sales transaction, thepoll including the customer fingerprint (509). For example,communication module 413 can send poll 497, including customerfingerprint 443, to receipt preferences database server 421. Poll 497requests receipt delivery preferences applicable to the salestransaction for customer 491. Communication module 442 can receive poll497 from POS system 411.

Method 500 includes using the customer fingerprint to locate applicablereceipt delivery preferences, including a printed receipt preference,for the sales transaction from within receipt preferences database(510). For example, database access module 463 can use customerfingerprint 443 to locate receipt delivery preferences 444 from withinreceipt preferences database 422. As described, receipt deliverypreferences 444 includes a printed receipt preference indicating whetheror not customer 491 desires a printed receipt for the sales transaction.

Method 500 includes returning the applicable receipt deliverypreferences, including the printed receipt preference, to thePoint-Of-Sale (POS) system at the one of the entity's store locations(511). Method 500 includes receiving the applicable receipt deliverypreferences, including the printed receipt preference, from the receiptdatabase server (512). For example, communication module 442 can returnreceipt delivery preferences 444 to POS system 411. Communication module413 can receive receipt delivery preferences 444 from receiptpreferences database server 421.

As described, POS system 411 can poll receipt preferences databaseserver 421 at specified intervals. The specified interval can be(potentially significantly) smaller than the time for completing a salestransition. For example, POS system 411 can poll receipt preferencesdatabase server 421 every second. The smaller specified interval canallow POS system 211 to detect changes to receipt delivery preferencesfor a customer even after a transaction has been opened for thecustomer.

For example, prior to the transaction for customer 491 being closed,mobile device 401 can receive input 494 from customer 491. Input 494 canspecify receipt delivery preferences 454 for sales tractions conductedwith POS system 411, as well as other commonly owned POS systems.Receipt delivery preferences 454 can include a printed receiptpreference indicating if customer 451 desires printed receipts for salestransactions. Receipt delivery preferences 454 can differ from receiptdelivery preferences 444. For example, receipt delivery preferences 444may specify that customer 491 never wants a paper receipt. On the otherhand, receipt delivery preferences 444 may specify that customer 491wants a paper receipt just for the next sales transaction.

Communication module 403 can send customer fingerprint 443 along withreceipt delivery preferences 454 to receipt preferences database server421. Web server 441 can receive customer fingerprint 443 along withreceipt delivery preferences 454 from mobile device 401. Database accessmodule 463 can store an association between customer fingerprint 443 andreceipt delivery preferences 454 in receipt preferences database 422(thus overwriting the previous association between customer fingerprint443 and receipt delivery preferences 444).

Subsequent to storage of the association between customer fingerprint443 and receipt delivery preferences 444 and prior to the salestransaction for customer 491 being closed, communication module 413 cansend poll 498, including customer fingerprint 443, to receiptpreferences database server 421. Poll 498 requests receipt deliverypreferences applicable to the sales transaction for customer 491.Communication module 442 can receive poll 498 from POS system 411.Database access module 463 can use customer fingerprint 443 to locatereceipt delivery preferences 454 from within receipt preferencesdatabase 422. Receipt delivery preferences 454 can include a printedreceipt preference (which may differ from a printed receipt preferencein receipt delivery preferences 444) indicating whether or not customer491 desires a printed receipt for the sales transaction.

If further changes to receipt delivery preferences are received atmobile device 401, the further changes can be sent to receiptpreferences database server 421 for storage in receipt preferencesdatabase 422. POS system 411 can continue to poll receipt preferencesdatabase server 421 for receipt delivery preferences for the salestransaction until the sales transaction is closed. Since the specifiedinterval (e.g., one second) is small relative to the time for completinga sales transaction, there is a significantly increased chance that POSsystem 411 can detect more (or even most) recent receipt deliverypreferences for a customer prior to a sales transaction closing.

Method 500 includes closing the sales transaction (513). For example,when each of the one or more items has been processed (e.g., scanned), acashier or customer 491 can enter commands at I/O peripherals 416 to endthe sales transaction. In response, I/O peripherals 416 can send closetransaction message 434 to transaction processor 412. Transactionprocessor 412 can receive close transaction message 434 from I/Operipherals 416. In response to close transaction message 434,transaction processor 412 can close the sales transaction processing theone or more items for customer 491.

Method 500 includes, in response to closing the sales transaction,outputting one or more types of receipts for the sales transaction(514). For example, in response to closing the sales transaction forcustomer 491, POS system 411 can output one or more types of receipts,such as, for example, digital and/or printed receipts, for the salestransaction.

Outputting one or more types of receipts for the sales transaction caninclude sending a digital receipt containing the collected receipt datato a mobile device that was previously paired to the customerfingerprint (515). For example, POS system 411 can send digital receipt461, including receipt data 433, to mobile device 401. Alternately, POSsystem 411 can send digital receipt 461, including receipt data 433, toreceipt preferences database server 421. Receipt preferences databaseserver 421 can store digital receipt 461. Receipt preferences databaseserver 421 can also store an association between customer fingerprint443 and receipt 461.

Outputting one or more types of receipts for the sales transaction caninclude printing a paper receipt containing the collected receipt datain accordance with the printed receipt preference (516). In someembodiments, receipt delivery preferences 444 specify that a paperreceipt is desired for the sales transaction. In these embodiments, anI/O peripheral, such as, for example, a receipt printer in I/Operipherals 416, can print receipt data 433 in paper receipt 462. Inother embodiments, receipt delivery preferences 444 specify that aprinted receipt is not desired for the sales transaction. In these otherembodiments, a paper receipt is not printed.

Method 500 includes receiving the digital receipt from the Point-Of-Sale(POS) system (517). For example, mobile device 401 can receive digitalreceipt 461, including receipt data 433, from POS system 411.Alternately, mobile device 401 can request digital receipts from receiptpreferences database server 421. For example, mobile device 401 can senda request to receipt preferences database server 421 for any digitalreceipts associated customer fingerprint 443. In response, receiptpreferences database server 421 can return digital receipts associatedwith customer fingerprint 443, including digital receipt 461, back tomobile device 401. Customer 491 can then view receipt data 433 on mobiledevice 201.

In embodiments where paper receipt 462 is printed, customer 491 can alsoobtain paper receipt 462, either directly (e.g., when doingself-checkout) or from a cashier.

Turning to FIG. 6, FIG. 6 illustrates an example schematic block diagramof a point-of-sale (POS) system 600. In some embodiments, the hardware,software, or hardware and software of POS system 600 may be configuredto implement one or more methods in accordance with the presentinvention. For example, POS system 600 may be manufactured, programmed,modified, or upgraded to support transferring digital receipt data tomobile devices. Any of POS systems 211 and 411 can be a POS systemsimilar to POS system 600.

POS system 600 can include various components. In some embodiments, POSsystem 600 includes a central or primary computer 612, a monitor 614(e.g., a cashier-facing monitor 614), one or more input devices 616(e.g., scanners 616 a, keyboards 616 b, scales, or the like), one ormore payment devices 618 (e.g., cash drawers 618 a, card readers 618 b)for receiving or returning payments, one or more output devices 620(e.g., customer-facing display 620 a or monitor 620 a, receipt printer620 b), or the like or combinations or sub-combinations thereof, and NFCmodule 622, such as, for example, an NFC dongle.

Computer 612 may form the backbone of POS system 600. Other components616, 618, 620, 622 forming part of a POS system 600 can communicate withcomputer 612. Input devices 616 and certain payment devices 618 can feeddata and commands to computer 612 for processing or implementation. Forexample, scanner 616 a can pass data communicating the identity of oneor more items to be purchased, returned, or the like to a computer 612.Similarly, card reader 618 b can pass payment information to computer612.

On the other hand, output devices 620 and certain payment devices 618can follow or implement commands issued by computer 612. For example,cash drawer 618 a may open in accordance with the commands of computer612. Similarly, customer-facing display 620 a and receipt printer 620 bcan display or output data or information as instructed by computer 612.

In some embodiments, in addition to handling consumer transactions(e.g., purchases, returns), POS system 600 can provide or supportcertain “back office” functionality. For example, POS system 600 canprovide or support inventory control, purchasing, receiving andtransferring products, or the like. POS system 600 can also store salesand customer information for reporting purposes, marketing purposes,receivables management, trend analysis, cost analysis, price analysis,profit analysis, or the like. If desired or necessary, POS system 600can include an accounting interface to pass certain information to oneor more in-house or independent accounting applications.

In some embodiments, POS system 600 operates substantiallyindependently, as a stand-alone unit. Alternately, POS system 600 may beone of several POS systems 600 forming the front line of a largersystem. FIG. 7 illustrates an example schematic block diagram of anetwork 700 of point-of-sale (POS) systems 600. For example, multiplePOS systems 600 may operate at a particular location 722 (e.g., within aretail, brick-and-mortar store). In such embodiments, the various POSsystems 600 may be interconnected via LAN 724. LAN 724 may also connectthe POS systems 600 to a local server 726.

Local server 726 can support the operation of the associated POS systems600. For example, a server 726 may provide a central repository fromwhich certain data needed by the associated POS systems 600 may bestored, indexed, accessed, or the like. Server 726 can serve certainsoftware to one or more POS systems 600. In certain embodiments, a POSsystem 600 can offload certain tasks, computations, verifications, orthe like to server 726.

Alternatively, or in addition thereto, server 726 can support certainback office functionality. For example, server 726 can receive andcompile (e.g., within an associated database 728) data from the variousassociated POS systems 600 to provide or support inventory control,purchasing, receiving and transferring products, or the like. Server 726can also receive and compile sales and customer information forreporting purposes, marketing purposes, receivables management, trendanalysis, cost analysis, price analysis, profit analysis, or the like.

In some embodiments, one or more POS systems 600 and/or servers 726corresponding to a particular location 722 can communicate with oraccess one or more remote computers or resources via one or more networkdevices 730. For example, a network device 730 can enable a POS system600 to contact outside resources and verify the payment credentials(e.g., credit card information) provided by a customer. A network device730 can comprise a modem, router, or the like.

In selected embodiments, POS systems 600 operate within anenterprise-wide system 731 comprising multiple locations 722 (e.g.,branches 722 or stores 722). In such embodiments, each location 722 mayhave one or more POS systems 600, local servers 726, local databases728, network devices 730, or the like or combinations orsub-combinations thereof connected by a computer network (e.g., a LAN724). It may be that any of data receipt servers 221 and 421 areincluded in and/or include the functionality of a local server 726.

Additionally, each such location 722 may be configured to interact withone or more supervisory systems 732. For example, multiple branchlocations 722 may report to an associated “headquarters” location orsystem. It may be that any of data receipt servers 221 and 421 areincluded in and/or include the functionality of a supervisory system732.

A supervisory system 732 can include one or more supervisory servers734, databases 736, workstations 738, network devices 740, or the likeor combinations or sub-combinations thereof. The various components of asupervisory system 732 can be interconnected via a computer network(e.g., a LAN 742). In selected embodiments, a supervisory system 732includes one or more supervisory servers 734 providing a centralrepository from which certain data needed by the one or more POS systems600 or local servers 726 may be stored, indexed, accessed, or the like.

Alternatively, or in addition thereto, a supervisory server 734 canreceive and compile (e.g., within an associated database 736) data fromthe various associated POS systems 600 or local servers 726 to provideor support inventory control, purchasing, receiving and transferringproducts, or the like. A supervisory server 734 may also receive andcompile sales and customer information for reporting purposes, marketingpurposes, receivables management, trend analysis, cost analysis, priceanalysis, profit analysis, or the like.

A supervisory system 732 can be connected to one or more associatedlocations 922 or branches 722 in via any suitable computer network 744(e.g., WAN 744). For example, in selected embodiments, one or morelocations 722 can connect to a supervisor system 732 via the Internet.Communication over such a network 744 can follow any suitable protocolor security scheme. For example, communication may utilize the FileTransfer Protocol (FTP), a virtual private network (VPN), intranet, orthe like.

Although the components and modules illustrated herein are shown anddescribed in a particular arrangement, the arrangement of components andmodules may be altered to process data in a different manner. In otherembodiments, one or more additional components or modules may be addedto the described systems, and one or more components or modules may beremoved from the described systems. Alternate embodiments may combinetwo or more of the described components or modules into a singlecomponent or module.

The foregoing description has been presented for the purposes ofillustration and description. It is not intended to be exhaustive or tolimit the invention to the precise form disclosed. Many modificationsand variations are possible in light of the above teaching. Further, itshould be noted that any or all of the aforementioned alternateembodiments may be used in any combination desired to form additionalhybrid embodiments of the invention.

Further, although specific embodiments of the invention have beendescribed and illustrated, the invention is not to be limited to thespecific forms or arrangements of parts so described and illustrated.The scope of the invention is to be defined by the claims appendedhereto, any future claims submitted here and in different applications,and their equivalents.

What is claimed:
 1. At a Point-Of-Sale (POS) computer system, the POScomputer system in a store location for an entity, the POS computersystem including one or more processors and system memory, a methodcomprising: syncing, using a POS communication module at the POScomputer system, a portion of a receipt preferences database from areceipt preferences database server being remote from the POS computersystem, the portion of the receipt preferences database being relevantto the store location at which the POS computer system is located, thereceipt preferences database storing, using a database access module,associations between derived customer identifiers for a plurality ofcustomers and corresponding customer specified receipt deliverypreferences that apply to sales transactions conducted with the entityfor the plurality of customers, the specified receipt deliverypreferences for each of the plurality of customers including a customerentered printed receipt preference, the customer entered printed receiptpreference indicating if the customer desires printed receipts to beprovided along with digital receipts for sales transactions at the storelocation; opening a sales transaction at the POS computer system;subsequent to opening the sales transaction, collecting receipt data forthe sales transaction using the POS computer system; acquiring thecustomer identifier associated with sales transaction, the customeridentifier corresponding to a customer and being derivable from afingerprint scanner of a mobile device associated with the customer suchthat the customer identifier comprises fingerprint data of the customer,the mobile device comprising one or more processors, a user interfacefor receiving input from the customer, a system memory comprising one ormore computer storage media having stored thereon computer-executableinstructions, and a mobile device communication module for communicatingwith the receipt preferences database server, wherein the mobile devicereceives customer input specifying receipt delivery preferences andsends the specified receipt delivery preferences and the customeridentifier with the mobile device communication module to the receiptpreferences database server and wherein the receipt preferences databaseserver receives, from the mobile device communication module, anindication of pairing of a device ID for the mobile device to thecustomer identifier; using, at the POS computer system, the customeridentifier derived from the fingerprint scanner to locate associatedreceipt delivery preferences for the customer and that are applicable tothe sales transaction from within the synced portion of the receiptpreferences database; closing the sales transaction at the POS computersystem; and in response to closing the sales transaction, the POScomputer system outputting one or more types of receipts for the salestransaction in accordance with the located receipt delivery preferencesfor the customer, including at least one of: sending a digital receiptcontaining the collected receipt data for a sales transaction from theentity to the mobile device associated with the customer identifier vianetwork communication wherein the digital receipt is presentable on adisplay of the mobile device; and printing a paper receipt containingthe collected receipt data based on the printed receipt preferenceincluded in the located receipt delivery preferences for the customer.2. The method of claim 1, wherein opening a sales transaction at the POScomputer system comprises receiving an indication from an I/O peripheralthat a sales transaction is to be opened.
 3. The method of claim 1,wherein collecting receipt data for the sales transaction, comprises foreach of one or more items included in the sales transaction: receivingan item identifier from a scanned bar code; and referring to a productdatabase to access item description data and item cost data for theitem.
 4. The method of claim 1, wherein closing the sales transaction atthe POS computer system comprises receiving an indication from an I/Operipheral that the sales transaction is to be closed.
 5. The method ofclaim 1, wherein printing a paper receipt containing the collectedreceipt data based on the printed receipt preference comprises printinga paper receipt based on a printed receipt preference that specifiespaper receipts are to be printed for all of the customer's salestransactions.
 6. The method of claim 1, wherein printing a paper receiptcontaining the collected receipt data based on the printed receiptpreference comprises printing a paper receipt based on a printed receiptpreference that specifies a paper receipt is to be printed for the salestransaction.
 7. The method of claim 1, wherein sending a digital receiptcomprises sending a digital receipt to the receipt preferences databaseserver.
 8. A computer program product for use at a Point-Of-Sale (POS)computer system, the POS computer system in a store location for anentity, the computer program product for implementing a method fordelivering customer specified receipt types at checkout, the computerprogram product comprising a computer storage device having storedthereon computer-executable instructions that, when executed at aprocessor, cause the POS computer system to perform the method,including the following: sync, using a POS communication module at thePOS computer system, a portion of a receipt preferences database from areceipt preferences database server being remote from the POS computersystem, the portion of the receipt preferences database being relevantto the store location at which the POS computer system is located, thereceipt preferences database storing, using a database access module,associations between derived customer identifiers for a plurality ofcustomers and corresponding customer specified receipt deliverypreferences that apply to sales transactions conducted with the entityfor the plurality of customers, the specified receipt deliverypreferences for each of the plurality of customers including a customerentered printed receipt preference, the customer entered printed receiptpreference indicating if the customer desires printed receipts to beprovided along with digital receipts for sales transactions at the storelocation; open a sales transaction at the POS computer system;subsequent to opening the sales transaction, collect receipt data forthe sales transaction at the POS computer system; acquire the customeridentifier associated with sales transaction, the customer identifiercorresponding to a customer and being derivable from a fingerprintscanner of a mobile device associated with the customer such that thecustomer identifier comprises fingerprint data of the customer, themobile device comprising one or more processors, a user interface forreceiving input from the customer, a system memory comprising one ormore computer storage media having stored thereon computer-executableinstructions, and a mobile device communication module for enabling thereceipt preferences database server to communicate with the mobiledevice, wherein the mobile device is configured to receive customerinput specifying receipt delivery preferences and to send the specifiedreceipt delivery preferences and the customer identifier with the mobiledevice communication module to the receipt preferences database serverand wherein the receipt preferences database server receives, from themobile device communication module, an indication of pairing of a deviceID for the mobile device to the customer identifier; use the customeridentifier derived from the fingerprint scanner to locate associatedreceipt delivery preferences for the customer and that are applicable tothe sales transaction from within the synced portion of the receiptpreferences database; close the sales transaction at the POS computersystem; and in response to closing the sales transaction, output one ormore types of receipts for the sales transaction in accordance with thelocated receipt delivery preferences for the customer, including atleast one of: send a digital receipt containing the collected receiptdata for a sales transaction from the entity to the mobile deviceassociated with the customer identifier via network connection whereinthe digital receipt is presentable on a display of the mobile device;and print a paper receipt containing the collected receipt data based onthe printed receipt preference included in the located receipt deliverypreferences for the customer.
 9. The computer program product of claim8, wherein computer-executable instructions that, when executed, causethe POS computer system to print a paper receipt containing thecollected receipt data based on the printed receipt preference comprisecomputer-executable instructions that, when executed, cause the POScomputer system to print a paper receipt based on a printed receiptpreference that specifies paper receipts are to be printed for all ofthe customer's sales transactions.
 10. The computer program product ofclaim 8, wherein computer-executable instructions that, when executed,cause the POS computer system to print a paper receipt containing thecollected receipt data based on the printed receipt preference comprisecomputer-executable instructions that, when executed, cause the POScomputer system to print a paper receipt based on a printed receiptpreference that specifies a paper receipt is to be printed for the salestransaction.
 11. The computer program product of claim 8, whereincomputer-executable instructions that, when executed, cause the POScomputer system to send a digital receipt to the receipt preferencesdatabase server.
 12. A system for delivering customer specified receipttypes at checkout, the system comprising: a receipt preferences databasefor an entity, the entity having one or more store locations, thereceipt preferences database storing associations between derivedcustomer identifiers for a plurality of customers and associatedcustomer specified receipt delivery preferences that apply to salestransactions conducted with the entity for the plurality of customers,the specified receipt delivery preferences for each of the plurality ofcustomers including a customer entered printed receipt preferenceindicating if the customer desires printed receipts to be provided alongwith digital receipts for sales transactions; a receipt preferencesdatabase server, the receipt preferences database server comprising: oneor more processors; system memory; a Web server for receiving customerspecified receipt delivery preferences and the customer identifier froma mobile device comprising one or more processors, a user interface forreceiving input from a user, a mobile device communication module, andsystem memory comprising one or more computer storage media havingstored thereon computer-executable instructions; a server communicationmodule for sending customer specified receipt delivery preferences tothe one or more store locations and being in communication with themobile device communication module for enabling the receipt preferencesdatabase server to communicate with the mobile device; and one or morecomputer storage media having stored thereon computer-executableinstructions that, when executed, cause the receipt preferences databaseserver to: receive customer specified receipt delivery preferences andthe customer identifier through the Web server from the mobile device,the customer specified receipt delivery preferences specified throughthe mobile device by customers of the entity wherein the mobile deviceis configured to receive customer input specifying receipt deliverypreferences and to send the specified receipt delivery preferences andthe customer identifier with the mobile device communication module tothe receipt preferences database server, the customer specified receiptdelivery preferences including printed receipt preferences for the oneor more store locations, the printed receipt preference indicating if acustomer desires printed receipts to be provided along with digitalreceipts for transactions; receive, from the mobile device communicationmodule, an indication of pairing of a device ID for the mobile device tothe customer identifier; store, using a database access module, anassociation between the customer identifier and the customer specifiedreceipt delivery preferences in the receipt preferences database; andsync a relevant portion of the receipt preferences database through theserver communication module to each of the one or more store locations;and a Point-Of-Sale (POS) computer system at each of the one or morelocations, the POS computer system being remote from the receiptpreferences database server and comprising: one or more processors;system memory; a POS communication module for receiving customerspecified receipt delivery preferences from the receipt preferencesdatabase server; one or more I/O peripherals for acquiring the customeridentifiers to be provided to the Web server; and one or more computerstorage media having stored thereon computer-executable instructionsthat, when executed, cause the POS computer system to: sync a portion ofthe receipt preferences database through the POS communication modulefrom the receipt preferences database server the portion of the receiptpreferences database being relevant to the store location at which thePOS computer system is located; open a sales transaction for a customer;subsequent to opening the sales transaction, collect receipt data forthe sales transaction; acquire the customer identifier associated withthe sales transaction, the customer identifier corresponding to acustomer and being derivable from a fingerprint scanner of the mobiledevice associated with the customer such that the customer identifiercomprises fingerprint data of the customer; use the customer identifierderived from the fingerprint scanner to locate associated receiptdelivery preferences for the customer and that are applicable to thesales transaction from within the synced portion of the receiptpreferences database; close the sales transaction; and in response toclosing the sales transaction, output one or more types of receipts forthe sales transaction in accordance with the located receipt deliverypreferences for the customer, including at least one of: send, vianetwork communication a digital receipt containing the collected receiptdata for a sales transaction from the entity to the mobile device thatwas previously paired to the customer identifier wherein the digitalreceipt is presentable on a display of the mobile device; and print apaper receipt containing the collected receipt data based on a printedreceipt preference included in the located receipt delivery preferencesfor the customer.
 13. The system of claim 12, whereincomputer-executable instructions that, when executed, cause the POScomputer system to print a paper receipt comprise computer-executableinstructions that, when executed, cause the POS computer system to printa paper receipt based on a printed receipt preference that specifiespaper receipts are to be printed for all of the customer's salestransactions.
 14. The system of claim 12, wherein computer-executableinstructions that, when executed, cause the POS computer system to printa paper receipt comprise computer-executable instructions that, whenexecuted, cause the POS computer system to print a paper receipt basedon a printed receipt preference that specifies a paper receipt is to beprinted for the sales transaction.
 15. The system of claim 12, whereincomputer-executable instructions that, when executed, cause the POScomputer system to output one or more types of receipts for the salestransaction consist of computer-executable instructions that, whenexecuted, cause the POS computer system to send a digital receipt to themobile device.